this (and all other gen_ai) event is not really usable without the rest of the GenAI convention it follows at least today

To make the usable:

1. we need to express event requirement level in the yaml.
2. find a way to link from here to the actual convention which consist of a group of events, spans and metrics.
3. Find ways to bring these notes https://github.com/thompson-tomo/semantic-conventions/blob/42a320708d1a5bbdaad4cb955765b8f9ef926d24/docs/gen-ai/gen-ai-events.md?plain=1#L20-L39 - without them someone who discovers this even without the convention might not know how to migrate.

When it comes to GenAI events, I don't see how event registry is helpful. It breaks coherent document in multiple pieces without solving any problem.

we need to express event requirement level in the yaml.

There is already a weaver issue for this open-telemetry/weaver#406

find a way to link from here to the actual convention which consist of a group of events, spans and metrics.

When #2518 is merged in the template used can add a link to the namespace page (currently commented out). Hence solving this. Also Grouping ties into open-telemetry/weaver#406

Find ways to bring these notes https://github.com/thompson-tomo/semantic-conventions/blob/42a320708d1a5bbdaad4cb955765b8f9ef926d24/docs/gen-ai/gen-ai-events.md?plain=1#L20-L39 - without them someone who discovers this even without the convention might not know how to migrate.

Agree and was already captured as open-telemetry/weaver#802

can we talk about the benefits we get from event registry in MD and moving event definitions away from the corresponding conventions?

benefits we get from event registry in MD

I no longer see it as an event registry, originally I did when first raising PR. It is now adding events to the namespace registry alongside the other signals. The benefits would be things like readability, discoverability & consistency.

moving event definitions away from the corresponding conventions

This I don't get, when #2518 is merged you will have a single gen-ai page which is automatically generated which contains tables describing all of the events & entities which are defined. This will grow to include metrics, spans & attributes once their definitions can be fully defined in yaml and tooling can handle it.

What I do agree with is the way in which implementations are defined, can and should be improved. I will see if I can come with an interim solution for gen-ai.

The notion of namespace is not clear and I'd recommend prototyping and socializing the end result before working on any new proposals. I don't believe it's productive to work on it without getting feedback and buy-in from @open-telemetry/specs-semconv-approvers

i was actioning what was discussed in the last semconv meeting where it was socialized the end result of having a page showcasing the events available and being able to select one to see more details. It was explicitly mentioned that this index page would grow to include the other signals.